Summary

On Windows release builds, launching VSCodeee caused a separate terminal/console window to appear with bun.exe running inside it (for vscode-neovim and other extensions). This did not happen on macOS.

The root cause was that bun.exe (a console-subsystem binary) was spawned without CREATE_NO_WINDOW (0x08000000) flag. When a GUI-subsystem parent process (Tauri app with windows_subsystem = "windows") spawns a console-subsystem child without this flag, Windows allocates a visible console window. Additionally, Stdio::inherit() on stdout contributed to the issue since the parent has no console in release builds.

Changes

• Add CREATE_NO_WINDOW flag to all std::process::Command and tokio::process::Command invocations on Windows (6 locations across 4 files)
• Change ExtHost sidecar stdout from Stdio::inherit() to Stdio::null() since the parent GUI process has no console in release builds
• Move CommandExt imports to module level with #[cfg(windows)] for consistency
• Add rustdoc comments to previously undocumented platform-specific helper functions

How to Test

1. Build a Windows release binary (npm run tauri:devwin or release build)
2. Launch the app
3. Verify no separate console/terminal window appears alongside the main VSCodeee window
4. Verify extensions load correctly (especially vscode-neovim)

🤖 Generated with Claude Code